Logo DBM DBM-6000 : Protocol Converter for HORUS


This protocol has been validated on DBM-6000 ARM controller on a RS-485 protocol converter. Interfacing has been developed with a Horus DDE Unit.

All the zones and detectors status can be monitored . There is no possibility for the DBM-6000 to modify any parameter or to (dis-)arm the Horus sytem.

To interface one Galaxy central to the DBM-6000, one Protocol Converter is needed.
A protocol converter can monitor up to 2000 points. This capacity is limited by the number of DinCool channels in the controller.



In the installation window, let us say that each item is a node.
 1) How to set up the system

 

1) How to set up the system :

 

  1. Add a RS-485 protocol converter on the controller.

  2. In the window “management of the devices on the main bus”, control that the model is "HORUS 6000" and the version is "1.25". If it is not the case, then burn the converter flash with the file named HORUS_RS.s24 .

  3. Add a single slave on the converter: the HORUS terminal.

  4. Add the messages sets. Each message is related to a particular zone. See below for details.

  5. Add detectors in these messages.

  6. TIPS :

2) Configuration of the protocol converter:

 

Name

Horus converter

 

Address

xxxx

mandatory

The serial number labelled on the protocol converter.

Protocol

Alarm Central

mandatory

Bauds

9600

mandatory

Bits

8

mandatory

Parity

None

mandatory

Number Retry

-

This is the number of times the message is repeated before the converter generates a fault on the bus. Not use here.

Rx Time out

-

This is the time interval before repeating a message not acknowledged. Not use here.

Rx Time Ready

-

This is the delay before sending the next message after an acknowledge. Not use here.






3) Configuration of the Horus node:

The Horus is a slave for the protocol converter.

Name

A denomination for the Horus Terminal

Address

1

Survey this connection

Not use here. See the workaround below.








4) Configuration of the messages nodes:

The tags are grouped by zones. A message contains one zone. There are 32 tags by zone and a total of 5 zones in the Horus sytem. On the tag label, there is a 3 digits number: the first digit is the zone.


Name

The zone name

Address

The number of the zone






5) Configuration of the tags nodes

In the DBM-6000, a tag is referred as a detector. The tags nodes must be put in the natural ascending order, starting with 1, without gap. On the tag label, there is a 3 digits number: the two last digits is the address. Empty addresses before the last used tag must be defined, others not.

When you create the detector( an Horus tag), this configuration popup is automatically displayed.
Later, when editing the channel properties, go in the installator sheet and click on 'input properties' or select the variable in the variable list of the Horus node.

As for any other DinCool channel, you can set alarms. In case of alarm, it is always immediate, the timer is not used.

Name

the tag name

Address

The 2 lasts digits of the tag

 






5.1 Channel properties :

States 0 to 6 only are meaningful. Set the text as shown in the figure.

Default status is 'watch'.

In case of detection, the status changes immediately and remains 30 seconds before going back to “watch” (except for missing tag: 65 sec, to avoid infinite toggling).

The alarm time-out should always be left on zero.




 

 

The default plan images :

Not known
Watch
Detection
Panic alarm
Not used

 

6)  Accessing variables with DinTalk:

Add an external variable of type integer. Select the wanted channel in the list.

Possible integer values are 0 to 6 depending on the tag status.

7)  Connection control:

If the protocol converter is disconnected from the controller, the controller detects the absence of communication and an error bus is generated immediately. The alarm programmed for main bus errors (if any) in the controller is started. Don't forget to set the 'Alarm on device offline' in the controllers properties.

To survey the DBM-6000/Horus connection:

The protocol used does not allow the DBM6000 to detect the disconnection. A workaround can be used using the « missing tag technique » : 
Program in the Horus system the address of an unexisting tag. The will cause an event «missing tag ».  This event is sent every minute by the Horus terminal.
In the DBM, the missing tag status stays 65 seconds. Program in DinTalk that controls this tag : when tag is off-line, the Horus connection is working, and when the tag goes on watch, it means that the converter doesn't receive any signal from the Horus terminal. Generate a DinTalk alarm in this case.

 

8) Cabling RS-232

    Wiring : RS232 cable: 3 wires                

Horus

Protocol converter (Modbus port)

Tx (RJ-11:2)

Rx Modbus

Gnd (RJ-11:3)

Gnd Modbus

-

Others: not connected.

See also the cabling diagrams in the general help of the DBM-6000.

9) Screen examples